Custom fake CBT flag for MSSQLClient via TDS.py#2098
Custom fake CBT flag for MSSQLClient via TDS.py#2098Dfte wants to merge 2 commits intofortra:masterfrom
Conversation
|
Hey @anadrianmanrique, any news on this one ? :P |
|
@Dfte hey there. This was not assigned to anyone. I think that's why it's been out of the radar. |
|
Hey! No problem :)!! That said, I believe we'll have to factorize CBT computation codes because for the moment we have implemented the following techniques:
(and we'll have to write the tls-exporter one at some point) These could be reused in others protocols so may be we'll have to create a ChannelBindingComputation.py code with all these functions at some point. |
|
ok, I think the best would be to implement for now CheckMSSQLStatus.py to test channel binding support. It could be added also information regarding #2122 later. After that we should probably discuss how to unify at least LDAP and MSSSQL into one script. Thanks! |
2 participants
Heyo team!
This PR adds a custom fake_cbt_value that we can use to detect whether CBT is required or not on a MSSQL database.
This will be used for an upcoming module (mssql_cbt) on nxc:
The variable is added to the login and kerberosLogin function and automatically set to None so that it doesn't change the entire toolkit built over tds.py
Let me know if you want a custom option for mssqlshell :)
See ya!